[POC] feat: same slot composability and real time proving #804
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AnshuJalan
force-pushed
the
surge-real-time-poc
branch
from
52be092 to
c574668
Compare
* refac: add short commit hash as tag for docker build * fix: image not found in staging when using commit hash
AnshuJalan
force-pushed
the
surge-real-time-poc
branch
from
4e92420 to
8fbd4a9
Compare
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
AnshuJalan
force-pushed
the
surge-real-time-poc
branch
from
bf7235f to
43f86c4
Compare
AnshuJalan
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Idea
We want the user to be able to perform an L1 -> L2 -> L1 transaction in the same L1 slot. For example:
L2Call)L1Call)Technicalities
UserOpto asurge_sendUserOpendpoint on Catalyst. This user op contains the bridge message for theL2Call.L2Calltransaction into the transaction list of the block it preconfirms.UserOpsubmission on L1 (Step 1) as a "fast signal" into the anchor txn of the L2 block it creates.L1Calls generated from theL2Callexecution of step 2.Proposal submission
A "multicall bundle" of 3 transactions are submitted on L1 in the exact sequence:
The POC is most understandable when we consider 1 block / batch and 1 user op / block.